After looking over our options and costs we are going to go with option C which gives us the most flexibility at this point. Out of all the repair risks R-01, R-03, R-04, and R-05 were all validated and have firm procedures in place. The project manager feels we have addressed these issues and are going to close these items out. We have to leave R-02 open because we cannot say with confidence that this risk is resolved, by the process flow being interrupted we could have the potential of delay of repair.
Team Status
Management Meeting Status
Week of 16 May
A lot has happened in a short amount of time. We have the repair guides completed and our engineering team has worked hard with Dapple to get a system in place for getting the latest device software versions available to us. We have set P-02 to a closed status.
Our software team has also created contingency plans for the user data backup plan. We are in the final stages of that process and we are confident that U-01, U-02, S-06, and P-03 are completed and closed out.
Team Status
Management Meeting Status
Week of 20 June
We are at the end of the project. Our engineering, software, and network teams have performed in an outstanding manner. We have completed the project with 83% of our risks in an acceptable range. The only area where we do not feel confident in is the repair process, R-02. From the technician prospective it has the potential to delay their work and not meet the ten day repair window. This case is only with the most complicated repairs; however, it is an acceptable risk if we only have a few items that this happens to. We have plans to correct these items and bring our total risk to 100% free of what we estimated.
We also have risk P-04 open because we could not come to any type of coordination with Dapple on product recalls. Since this is a sore subject we decided to do our own trend analysis and consider this an acceptable risk.
The remaining risk U-03 was unable to be resolved because of the nature of the risk. With the web site linked to the repair process the user should be able to check the status of their repair. While we tested this in our lab we are not confident in how the situation will be resolved with heavy user activity. We considered this to be an acceptable risk.
Journal Entry
Week of 2 May
After looking over our options and costs we are going to go with option C which gives us the most flexibility at this point. Out of all the repair risks R-01, R-03, R-04, and R-05 were all validated and have firm procedures in place. The project manager feels we have addressed these issues and are going to close these items out. We have to leave R-02 open because we cannot say with confidence that this risk is resolved, by the process flow being interrupted we could have the potential of delay of repair.
Week of 16 May
A lot has happened in a short amount of time. We have the repair guides completed and our engineering team has worked hard with Dapple to get a system in place for getting the latest device software versions available to us. We have set P-02 to a closed status.
Our software team has also created contingency plans for the user data backup plan. We are in the final stages of that process and we are confident that U-01, U-02, S-06, and P-03 are completed and closed out.
Week of 20 June
We are at the end of the project. Our engineering, software, and network teams have performed in an outstanding manner. We have completed the project with 83% of our risks in an acceptable range. The only area where we do not feel confident in is the repair process, R-02. From the technician prospective it has the potential to delay their work and not meet the ten day repair window. This case is only with the most complicated repairs; however, it is an acceptable risk if we only have a few items that this happens to. We have plans to correct these items and bring our total risk to 100% free of what we estimated.
We also have risk P-04 open because we could not come to any type of coordination with Dapple on product recalls. Since this is a sore subject we decided to do our own trend analysis and consider this an acceptable risk.
The remaining risk U-03 was unable to be resolved because of the nature of the risk. With the web site linked to the repair process the user should be able to check the status of their repair. While we tested this in our lab we are not confident in how the situation will be resolved with heavy user activity. We considered this to be an acceptable risk.
Project Home Next Section